Skip to content

Conversation

@cgwalters
Copy link
Collaborator

This suddenly started in our RPM (COPR/mock) builds, my suspicion is that seccomp got turned on inadvertently, but let's add some error context here on general principle.

thread 'boundimage::tests::test_parse_spec_dir' panicked at crates/lib/src/boundimage.rs:290:49:
called `Result::unwrap()` on an `Err` value: Querying bound images

Caused by:
    Function not implemented (os error 38)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@github-actions github-actions bot added the area/ostree Issues related to ostree label Oct 19, 2025
@bootc-bot bootc-bot bot requested a review from henrywang October 19, 2025 22:40
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request enhances error handling by adding more context to operations that might fail, which is a great improvement for debuggability. The changes in crates/ostree-ext/src/globals.rs correctly use anyhow::Context and fn-error-context to wrap potential errors with descriptive messages. I have one piece of feedback regarding a likely missing import for the #[context] attribute macro.

This suddenly started in our RPM (COPR/mock) builds, my suspicion
is that seccomp got turned on inadvertently, but let's
add some error context here on general principle.

```
thread 'boundimage::tests::test_parse_spec_dir' panicked at crates/lib/src/boundimage.rs:290:49:
called `Result::unwrap()` on an `Err` value: Querying bound images

Caused by:
    Function not implemented (os error 38)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

Signed-off-by: Colin Walters <[email protected]>
@cgwalters cgwalters changed the title ostree-ext: Add .context for some more errors work around COPR regression Oct 21, 2025
@cgwalters cgwalters changed the title work around COPR regression work around mock (COPR) regression Oct 21, 2025
@cgwalters
Copy link
Collaborator Author

cgwalters commented Oct 21, 2025

Man I really should have looked carefully at the full list of failing tests. There were a ton from the importer failing, but that wasn't all of it. This seccomp profile turns of all use of openat2 which is going to be painful to work around consistently; we also use it in the linting code, etc.

@cgwalters
Copy link
Collaborator Author

OK I just turned off all the unit tests in the RPM build if we detect seccomp for now. We already do run the unit tests inside the container build, and this only affects COPR not production Koji so there's no real coverage loss.

@cgwalters cgwalters enabled auto-merge (rebase) October 21, 2025 21:17
@cgwalters
Copy link
Collaborator Author

@henrywang you're assigned reviewer this cycle, can you take this?

@cgwalters cgwalters merged commit b848577 into bootc-dev:main Oct 22, 2025
35 of 36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ostree Issues related to ostree

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants